keywords: ip pbx voip gateway gsm gateway

×

Notice

The forum is in read only mode.
× Technical information on install and config asterisk, zaptel under different OSs

Problem when I restart my box

15 years 4 months ago #2457 by james.zhu
hello,
what is the error? try to load fxo first and then 4e1 driver.
regards!
James.zhu

15 years 4 months ago #2459 by rcuadra
The error is in boot:

ZT_SPANCONFIG failed on span 1: Invalid argumen
15 years 4 months ago #2460 by james.zhu
hello,
what is your FXO card, is it a800p/a1200p or a400p? can you show lspci -vvvvvvvvv. i think the error caused by hardware detection.
regards!
James.zhu

15 years 4 months ago #2461 by rcuadra
The hardware is:

A400P for 4 FXO
D410P for 4 E1 ISDN card

I change the card position and the error continue.

Sure, is hardware detection in boot.

But How can I do to fix this problem.

Also I have other server with a800p and D210E and the problem is the same.
15 years 4 months ago #2462 by rcuadra
0d:03.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: Unknown device b100:0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr+ DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 32000ns max)
Interrupt: pin A routed to IRQ 82
Region 0: I/O ports at dc00
Region 1: Memory at fc6ff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0e:04.0 Communication controller: Digium, Inc. Wildcard TE410P quad-span T1/E1/J1 card 3.3V (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Interrupt: pin A routed to IRQ 90
Region 0: Memory at fc4ffc00 (32-bit, non-prefetchable)
15 years 4 months ago #2463 by james.zhu
hello,
I think you have to disable zaptel in udev and then use service zaptel start to load the driver. the sequence of load zaptel is wrong.
regards!
James.zhu

Time to create page: 0.035 seconds
Powered by Kunena Forum